home *** CD-ROM | disk | FTP | other *** search
- Path: hermes.ridgefield.sdr.slb.com!usenet
- From: "Warren D. MacEvoy jr." <macevoy@cims.nyu.edu>
- Newsgroups: comp.lang.c++
- Subject: Re: Name-mangling standard
- Date: Fri, 05 Jan 1996 19:19:31 -0500
- Organization: Courant Institute
- Message-ID: <30EDC013.7C780E5E@cims.nyu.edu>
- References: <20c.32169.607@newage.com.ar> <4bsnbu$5mu@mujibur.inmind.com>
- NNTP-Posting-Host: slip24.ridgefield.sdr.slb.com
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 2.0b3 (X11; I; Linux 1.1.62 i486)
-
- mfinney@inmind.com wrote:
- >
- > In <20c.32169.607@newage.com.ar>, juan.jose.comellas@newage.com.ar (Juan Jose Comellas) writes:
- > >Is anyone aware of any ANSI/ISO standard for name-mangling in C++? I
- > >currently work with several different C++ compilers and I sometimes
- > >want to compile a part of the project with one compiler and another
- > >part with another one, but different schemes for name-mangling make
- > >this impossible.
- >
- > I certainly hope not! Name mangling is a solution to passing type
- > information to 1950's linkers. Once linkers become more sophisticated,
- > name mangling can disappear back into the slime from which it came.
- >
- [snip]
- An alternative answer is given in a g++ faq (somewhere). Roughly,
- different implementations C++ have (obviously?) different
- implementations of, say, virtual function resolution. If vendors
- used the same Mangling Scheme, then codes compliled by different
- vendors would compile together, but would not necc. run correctly.
-
- If mangaling where specified, then other implementation-dependent
- components of the scheme need to be specified concurrently. As
- mfinney@inmind.com's post suggests, laying down law like this would,
- IMHO, tie the language to old linker technology.
-
- -- :o) Warren D. MacEvoy, macevoy@cims.nyu.edu
-